Permissive access control for modular reflection

ABSTRACT

Access to a module element within a first module by a second module is prohibited if the module element within the first module has not been exposed to the second module. If a particular module element within a first module has been exposed to a second module, then access to the particular module element by the second module may or may not be allowed depending on: (a) whether the particular module element has been declared with a public or non-public access modifier, (b) whether a second exposed module element, which includes the particular module element, has been declared with a public or non-public access modifier, (c) a level of access associated with the operation that attempts to access the particular module element of the first module, and/or (d) whether an accessibility override configuration is set for accessing the particular module element.

BENEFIT CLAIM Incorporation by Reference

This application claims benefit to the priority filing date of provisional application 62/209,878 filed on Aug. 25, 2015 which is hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to module systems. In particular, the present disclosure relates to controlling access to exposed module elements in a module system.

BACKGROUND

A module system permits the definition of a set of modules. Each module in a module system corresponds to a respective collection of code. A module system specifies how a collection of code corresponding to a particular module can access code corresponding to other modules. A module descriptor (interchangeably referred to as a “module interface”), for a particular module, expresses other modules upon which the particular module may depend. The declaration of a dependency on another module may be referred to as an explicit dependency. A module descriptor also expresses the elements of a particular module that are exposed by the particular module to the other modules which declare an explicit dependency on the particular module. Other modules which do not declare an explicit dependency on the particular module are restricted from accessing such elements.

Conventionally, module systems are designed to allow certain access techniques and/or accessibility configurations to override access restrictions declared in a module descriptor. In one example, reflective Application Programming Interfaces (APIs) (such as java.lang.reflect in Java SE) allow a test framework module to access a module element within a particular module even if that module element has not been exposed by the particular module to the test framework module. In another example, the .NET platform's reflective API allows for access to the internals of any module.

The approaches described in this section are approaches that could be pursued, but not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and they mean at least one. In the drawings:

FIG. 1 illustrates an example computing architecture in which techniques described herein may be practiced.

FIG. 2 is a block diagram illustrating one embodiment of a computer system suitable for implementing methods and features described herein.

FIG. 3 illustrates an example virtual machine memory layout in block diagram form according to an embodiment.

FIG. 4 illustrates an example of a module in the Java Module System in accordance with one or more embodiments.

FIG. 5 illustrates operations in accordance with one or more embodiments.

FIG. 6 illustrates a system in accordance with one or more embodiments.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding. One or more embodiments may be practiced without these specific details. Features described in one embodiment may be combined with features described in a different embodiment. In some examples, well-known structures and devices are described with reference to a block diagram form in order to avoid unnecessarily obscuring the present invention.

-   -   1. GENERAL OVERVIEW     -   2. ARCHITECTURAL OVERVIEW         -   2.1 EXAMPLE CLASS FILE STRUCTURE         -   2.2 EXAMPLE VIRTUAL MACHINE ARCHITECTURE         -   2.3 LOADING, LINKING, AND INITIALIZING     -   3. MODULE ELEMENTS OF A MODULE IN A MODULE SYSTEM     -   4. ACCESS KINDS FOR ACCESSING MODULE ELEMENTS     -   5. CONTROLLING ACCESS TO MODULE ELEMENTS     -   6. MISCELLANEOUS; EXTENSIONS     -   7. HARDWARE OVERVIEW

1. General Overview

One or more embodiments include strictly controlling access to modules in a module system.

In one embodiment, access to a module element within a first module by a second module is strictly prohibited if the module element within the first module has not been exposed to the second module. Access to the non-exposed module element of the first module by the second module is strictly prohibited regardless of (a) whether the non-exposed module element has been declared with a public or non-public access modifier, (b) the level of access associated with the operation that attempts to access the non-exposed module element of the first module, and (c) whether an accessibility override configuration is set for the non-exposed module element. In an example, access by a consumer module to a non-exposed module element of a provider module is prohibited even when access is attempted using a reflective operation with an accessibility override configuration being set for attempting to access the non-exposed module element.

In an example, access to a non-exposed module element within a first module by a second module is strictly prohibited even when the access is attempted using reflective operations with an accessibility override configuration that sets the non-exposed module element to be publicly accessible.

In an embodiment, if a particular module element within a first module has been exposed to a second module, then access to the particular module element by the second module may or may not be allowed. Permissions for accessing the exposed particular module element may be determined based on one or more factors including, but not limited to: (a) whether the particular module element has been declared with a public or non-public access modifier, (b) whether a second exposed module element, which includes the particular module element, has been declared with a public or non-public access modifier, (c) the level of access associated with the operation that attempts to access the non-exposed module element of the first module, and (d) whether an accessibility override configuration is set for the non-exposed module element.

In an example, a module element, in a first module, is a field declaration with a non-public access modifier. The field declaration is within a class declaration with a public access modifier. Both the field declaration and the class declaration are exposed by way of exposing a package which includes the class declaration (and as a result, the field declaration). If a second module attempts to access the field declaration (with the non-public access modifier) using a reflective operation, access is allowed or prohibited based on whether or not the reflective operation sets an accessibility override configuration for the field declaration. If the accessibility override configuration is not set, the non-public access modifier in the field declaration dictates that the second module is prohibited from accessing the field declaration. If the accessibility override configuration is set, the non-public access modifier in the field declaration is overridden and the second module is allowed to access the field declaration.

One or more embodiments described in this Specification and/or recited in the claims may not be included in this General Overview section.

2. Architectural Overview

FIG. 1 illustrates an example architecture in which techniques described herein may be practiced. Software and/or hardware components described with relation to the example architecture may be omitted or associated with a different set of functionality than described herein. Software and/or hardware components, not described herein, may be used within an environment in accordance with one or more embodiments. Accordingly, the example environment should not be constructed as limiting the scope of any of the claims.

As illustrated in FIG. 1, a computing architecture 100 includes source code files 101 which are compiled by a compiler 102 into class files 103 representing the program to be executed. The class files 103 are then loaded and executed by an execution platform 112, which includes a runtime environment 113, an operating system 111, and one or more application programming interfaces (APIs) 110 that enable communication between the runtime environment 113 and the operating system 111. The runtime environment 112 includes a virtual machine 104 comprising various components, such as a memory manager 105 (which may include a garbage collector), a class file verifier 106 to check the validity of class files 103, a class loader 107 to locate and build in-memory representations of classes, an interpreter 108 for executing the virtual machine 104 code, and a just-in-time (JIT) compiler 109 for producing optimized machine-level code.

In an embodiment, the computing architecture 100 includes source code files 101 that contain code that has been written in a particular programming language, such as Java, C, C++, C#, Ruby, Perl, and so forth. Thus, the source code files 101 adhere to a particular set of syntactic and/or semantic rules for the associated language. For example, code written in Java adheres to the Java Language Specification. However, since specifications are updated and revised over time, the source code files 101 may be associated with a version number indicating the revision of the specification to which the source code files 101 adhere. The exact programming language used to write the source code files 101 is generally not critical.

In various embodiments, the compiler 102 converts the source code, which is written according to a specification directed to the convenience of the programmer, to either machine or object code, which is executable directly by the particular machine environment, or an intermediate representation (“virtual machine code/instructions”), such as bytecode, which is executable by a virtual machine 104 that is capable of running on top of a variety of particular machine environments. The virtual machine instructions are executable by the virtual machine 104 in a more direct and efficient manner than the source code. Converting source code to virtual machine instructions includes mapping source code functionality from the language to virtual machine functionality that utilizes underlying resources, such as data structures. Often, functionality that is presented in simple terms via source code by the programmer is converted into more complex steps that map more directly to the instruction set supported by the underlying hardware on which the virtual machine 104 resides.

In general, programs are executed either as a compiled or an interpreted program. When a program is compiled, the code is transformed globally from a first language to a second language before execution. Since the work of transforming the code is performed ahead of time; compiled code tends to have excellent run-time performance. In addition, since the transformation occurs globally before execution, the code can be analyzed and optimized using techniques such as constant folding, dead code elimination, inlining, and so forth. However, depending on the program being executed, the startup time can be significant. In addition, inserting new code would require the program to be taken offline, re-compiled, and re-executed. For many dynamic languages (such as Java) which are designed to allow code to be inserted during the program's execution, a purely compiled approach may be inappropriate. When a program is interpreted, the code of the program is read line-by-line and converted to machine-level instructions while the program is executing. As a result, the program has a short startup time (can begin executing almost immediately), but the run-time performance is diminished by performing the transformation on the fly. Furthermore, since each instruction is analyzed individually, many optimizations that rely on a more global analysis of the program cannot be performed.

In some embodiments, the virtual machine 104 includes an interpreter 108 and a JIT compiler 109 (or a component implementing aspects of both), and executes programs using a combination of interpreted and compiled techniques. For example, the virtual machine 104 may initially begin by interpreting the virtual machine instructions representing the program via the interpreter 108 while tracking statistics related to program behavior, such as how often different sections or blocks of code are executed by the virtual machine 104. Once a block of code surpass a threshold (is “hot”), the virtual machine 104 invokes the JIT compiler 109 to perform an analysis of the block and generate optimized machine-level instructions which replaces the “hot” block of code for future executions. Since programs tend to spend most time executing a small portion of overall code, compiling just the “hot” portions of the program can provide similar performance to fully compiled code, but without the start-up penalty. Furthermore, although the optimization analysis is constrained to the “hot” block being replaced, there still exists far greater optimization potential than converting each instruction individually. There are a number of variations on the above described example, such as tiered compiling.

In order to provide clear examples, the source code files 101 have been illustrated as the “top level” representation of the program to be executed by the execution platform 111. Although the computing architecture 100 depicts the source code files 101 as a “top level” program representation, in other embodiments the source code files 101 may be an intermediate representation received via a “higher level” compiler that processed code files in a different language into the language of the source code files 101. Some examples in the following disclosure assume that the source code files 101 adhere to a class-based object-oriented programming language. However, this is not a requirement to utilizing the features described herein.

In an embodiment, compiler 102 receives as input the source code files 101 and converts the source code files 101 into class files 103 that are in a format expected by the virtual machine 104. For example, in the context of the JVM, the Java Virtual Machine Specification defines a particular class file format to which the class files 103 are expected to adhere. In some embodiments, the class files 103 contain the virtual machine instructions that have been converted from the source code files 101. However, in other embodiments, the class files 103 may contain other structures as well, such as tables identifying constant values and/or metadata related to various structures (classes, fields, methods, and so forth).

The following discussion assumes that each of the class files 103 represents a respective “class” defined in the source code files 101 (or dynamically generated by the compiler 102/virtual machine 104). However, the aforementioned assumption is not a strict requirement and will depend on the implementation of the virtual machine 104. Thus, the techniques described herein may still be performed regardless of the exact format of the class files 103. In some embodiments, the class files 103 are divided into one or more “libraries” or “packages”, each of which includes a collection of classes that provide related functionality. For example, a library may contain one or more class files that implement input/output (1/0) operations, mathematics tools, cryptographic techniques, graphics utilities, and so forth. Further, some classes (or fields/methods within those classes) may include access restrictions that limit their use to within a particular class/library/package or to classes with appropriate permissions.

2.1 Example Class File Structure

FIG. 2 illustrates an example structure for a class file 200 in block diagram form according to an embodiment. In order to provide clear examples, the remainder of the disclosure assumes that the class files 103 of the computing architecture 100 adhere to the structure of the example class file 200 described in this section. However, in a practical environment, the structure of the class file 200 will be dependent on the implementation of the virtual machine 104. Further, one or more features discussed herein may modify the structure of the class file 200 to, for example, add additional structure types. Therefore, the exact structure of the class file 200 is not critical to the techniques described herein. For the purposes of Section 2.1, “the class” or “the present class” refers to the class represented by the class file 200.

In FIG. 2, the class file 200 is made up of class members including, but not limited to, a constant table 201, field structures 208, class metadata 204, and method structures 209. In an embodiment, the constant table 201 is a data structure which, among other functions, acts as a symbol table for the class. For example, the constant table 201 may store data related to the various identifiers used in the source code files 101 such as type, scope, contents, and/or location. The constant table 201 has entries for value structures 202 (representing constant values of type int, long, double, float, byte, string, and so forth), class information structures 203, name and type information structures 205, field reference structures 206, and method reference structures 207 derived from the source code files 101 by the compiler 102. In an embodiment, the constant table 201 is implemented as an array that maps an index i to structure j. However, the exact implementation of the constant table 201 is not critical.

In some embodiments, the entries of the constant table 201 include structures which index other constant table 201 entries. For example, an entry for one of the value structures 202 representing a string may hold a tag identifying its “type” as string and an index to one or more other value structures 202 of the constant table 201 storing char, byte or int values representing the ASCII characters of the string.

In an embodiment, field reference structures 206 of the constant table 201 hold an index into the constant table 201 to one of the class information structures 203 representing the class defining the field and an index into the constant table 201 to one of the name and type information structures 205 that provides the name and descriptor of the field. Method reference structures 207 of the constant table 201 hold an index into the constant table 201 to one of the class information structures 203 representing the class defining the method and an index into the constant table 201 to one of the name and type information structures 205 that provides the name and descriptor for the method. The class information structures 203 hold an index into the constant table 201 to one of the value structures 202 holding the name of the associated class.

The name and type information structures 205 hold an index into the constant table 201 to one of the value structures 202 storing the name of the field/method and an index into the constant table 201 to one of the value structures 202 storing the descriptor.

In an embodiment, class metadata 204 includes metadata for the class, such as version number(s), number of entries in the constant pool, number of fields, number of methods, access flags (whether the class is public, non-public, final, abstract, etc.), an index to one of the class information structures 203 of the constant table 201 that identifies the present class, an index to one of the class information structures 203 of the constant table 201 that identifies the superclass (if any), and so forth.

In an embodiment, the field structures 208 represent a set of structures that identifies the various fields of the class. The field structures 208 store, for each field of the class, accessor flags for the field (whether the field is static, public, non-public, final, etc.), an index into the constant table 201 to one of the value structures 202 that holds the name of the field, and an index into the constant table 201 to one of the value structures 202 that holds a descriptor of the field.

In an embodiment, the method structures 209 represent a set of structures that identifies the various methods of the class. The method structures 209 store, for each method of the class, accessor flags for the method (e.g. whether the method is static, public, non-public, synchronized, etc.), an index into the constant table 201 to one of the value structures 202 that holds the name of the method, an index into the constant table 201 to one of the value structures 202 that holds the descriptor of the method, and the virtual machine instructions that correspond to the body of the method as defined in the source code files 101.

In an embodiment, a descriptor represents a type of a field or method. For example, the descriptor may be implemented as a string adhering to a particular syntax. While the exact syntax is not critical, a few examples are described below.

In an example where the descriptor represents a type of the field, the descriptor identifies the type of data held by the field. In an embodiment, a field can hold a basic type, an object, or an array. When a field holds a basic type, the descriptor is a string that identifies the basic type (e.g., “B”=byte, “C”=char, “D”=double, “F”=float, “I”=int, “J”=long int, etc.). When a field holds an object, the descriptor is a string that identifies the class name of the object (e.g. “L ClassName”). “L” in this case indicates a reference, thus “L ClassName” represents a reference to an object of class ClassName. When the field is an array, the descriptor identifies the type held by the array. For example, “[B” indicates an array of bytes, with “[” indicating an array and “B” indicating that the array holds the basic type of byte. However, since arrays can be nested, the descriptor for an array may also indicate the nesting. For example, “[[L ClassName” indicates an array where each index holds an array that holds objects of class ClassName. In some embodiments, the ClassName is fully qualified and includes the simple name of the class, as well as the pathname of the class. For example, the ClassName may indicate where the file is stored in the package, library, or file system hosting the class file 200.

In the case of a method, the descriptor identifies the parameters of the method and the return type of the method. For example, a method descriptor may follow the general form “({ParameterDescriptor}) ReturnDescriptor”, where the {ParameterDescriptor} is a list of field descriptors representing the parameters and the ReturnDescriptor is a field descriptor identifying the return type. For instance, the string “V” may be used to represent the void return type. Thus, a method defined in the source code files 101 as “Object m (int I, double d, Thread t) { . . . }” matches the descriptor “(I D L Thread) L Object”.

In an embodiment, the virtual machine instructions held in the method structures 209 include operations which reference entries of the constant table 201. Using Java as an example, consider the following class:

class A { int add12and13( ) { return B.addTwo(12, 13); } }

In the above example, the Java method add12andl3 is defined in class A, takes no parameters, and returns an integer. The body of method add12and13 calls static method addTwo of class B which takes the constant integer values 12 and 13 as parameters, and returns the result. Thus, in the constant table 201, the compiler 102 includes, among other entries, a method reference structure that corresponds to the call to the method B.addTwo. In Java, a call to a method compiles down to an invoke command in the bytecode of the JVM (in this case invokestatic as addTwo is a static method of class B). The invoke command is provided an index into the constant table 201 corresponding to the method reference structure that identifies the class defining addTwo “B”, the name of addTwo “addTwo”, and the descriptor of addTwo “(I I)I”. For example, assuming the aforementioned method reference is stored at index 4, the bytecode instruction may appear as “invokestatic #4”.

Since the constant table 201 refers to classes, methods, and fields symbolically with structures carrying identifying information, rather than direct references to a memory location, the entries of the constant table 201 are referred to as “symbolic references”. One reason that symbolic references are utilized for the class files 103 is because, in some embodiments, the compiler 102 is unaware of how and where the classes will be stored once loaded into the runtime environment 112. As will be described in Section 2.3, eventually the run-time representation of the symbolic references are resolved into actual memory addresses by the virtual machine 104 after the referenced classes (and associated structures) have been loaded into the runtime environment and allocated concrete memory locations.

2.2 Example Virtual Machine Architecture

FIG. 3 illustrates an example virtual machine memory layout 300 in block diagram form according to an embodiment. In order to provide clear examples, the remaining discussion will assume that the virtual machine 104 adheres to the virtual machine memory layout 300 depicted in FIG. 3. In addition, although components of the virtual machine memory layout 300 may be referred to as memory “areas”, there is no requirement that the memory areas are contiguous.

In the example illustrated by FIG. 3, the virtual machine memory layout 300 is divided into a shared area 301 and a thread area 307. The shared area 301 represents an area in memory where structures shared among the various threads executing on the virtual machine 104 are stored. The shared area 301 includes a heap 302 and a per-class area 303. In an embodiment, the heap 302 represents the run-time data area from which memory for class instances and arrays is allocated. In an embodiment, the per-class area 303 represents the memory area where the data pertaining to the individual classes are stored. In an embodiment, the per-class area 303 includes, for each loaded class, a run-time constant pool 304 representing data from the constant table 201 of the class, field and method data 306 (for example, to hold the static fields of the class), and the method code 305 representing the virtual machine instructions for methods of the class.

The thread area 307 represents a memory area where structures specific to individual threads are stored. In FIG. 3, the thread area 307 includes thread structures 308 and thread structures 311, representing the per-thread structures utilized by different threads. In order to provide clear examples, the thread area 307 depicted in FIG. 3 assumes two threads are executing on the virtual machine 104. However, in a practical environment, the virtual machine 104 may execute any arbitrary number of threads, with the number of thread structures scaled accordingly.

In an embodiment, thread structures 308 includes program counter 309 and virtual machine stack 310. Similarly, thread structures 311 includes program counter 312 and virtual machine stack 313. In an embodiment, program counter 309 and program counter 312 store the current address of the virtual machine instruction being executed by their respective threads.

Thus, as a thread steps through the instructions, the program counters are updated to maintain an index to the current instruction. In an embodiment, virtual machine stack 310 and virtual machine stack 313 each store frames for their respective threads that hold local variables and partial results, and is also used for method invocation and return.

In an embodiment, a frame is a data structure used to store data and partial results, return values for methods, and perform dynamic linking. A new frame is created each time a method is invoked. A frame is destroyed when the method that caused the frame to be generated completes. Thus, when a thread performs a method invocation, the virtual machine 104 generates a new frame and pushes that frame onto the virtual machine stack associated with the thread.

When the method invocation completes, the virtual machine 104 passes back the result of the method invocation to the previous frame and pops the current frame off of the stack. In an embodiment, for a given thread, one frame is active at any point. This active frame is referred to as the current frame, the method that caused generation of the current frame is referred to as the current method, and the class to which the current method belongs is referred to as the current class.

2.3 Loading, Linking, and Initializing

In an embodiment, the virtual machine 104 dynamically loads, links, and initializes classes. Loading is the process of finding a class with a particular name and creating a representation from the associated class file 200 of that class within the memory of the runtime environment 112. For example, creating the run-time constant pool 304, method code 305, and field and method data 306 for the class within the per-class area 303 of the virtual machine memory layout 300. Linking is the process of taking the in-memory representation of the class and combining it with the run-time state of the virtual machine 104 so that the methods of the class can be executed. Initialization is the process of executing the class constructors to set the starting state of the field and method data 306 of the class and/or create class instances on the heap 302 for the initialized class.

The following are examples of loading, linking, and initializing techniques that may be implemented by the virtual machine 104. However, in many embodiments the steps may be interleaved, such that an initial class is loaded, then during linking a second class is loaded to resolve a symbolic reference found in the first class, which in turn causes a third class to be loaded, and so forth. Thus, progress through the stages of loading, linking, and initializing can differ from class to class. Further, some embodiments may delay (perform “lazily”) one or more functions of the loading, linking, and initializing process until the class is actually required. For example, resolution of a method reference may be delayed until a virtual machine instruction invoking the method is executed. Thus, the exact timing of when the steps are performed for each class can vary greatly between implementations.

To begin the loading process, the virtual machine 104 starts up by invoking the class loader 107 which loads an initial class. The technique by which the initial class is specified will vary from embodiment to embodiment. For example, one technique may have the virtual machine 104 accept a command line argument on startup that specifies the initial class.

To load a class, the class loader 107 parses the class file 200 corresponding to the class and determines whether the class file 200 is well-formed (meets the syntactic expectations of the virtual machine 104). If not, the class loader 107 generates an error. For example, in Java the error might be generated in the form of an exception which is thrown to an exception handler for processing. Otherwise, the class loader 107 generates the in-memory representation of the class by allocating the run-time constant pool 304, method code 305, and field and method data 306 for the class within the per-class area 303.

In some embodiments, when the class loader 107 loads a class, the class loader 107 also recursively loads the super-classes of the loaded class. For example, the virtual machine 104 may ensure that the superclasses of a particular class are loaded, linked, and/or initialized before proceeding with the loading, linking and initializing process for the particular class.

During linking, the virtual machine 104 verifies the class, prepares the class, and performs resolution of the symbolic references defined in the run-time constant pool 304 of the class.

To verify the class, the virtual machine 104 checks whether the in-memory representation of the class is structurally correct. For example, the virtual machine 104 may check that each class except the generic class Object has a superclass, check that final classes have no sub-classes and final methods are not overridden, check whether constant pool entries are consistent with one another, check whether the current class has correct access permissions for classes/fields/structures referenced in the constant pool 304, check that the virtual machine 104 code of methods will not cause unexpected behavior (e.g. making sure a jump instruction does not send the virtual machine 104 beyond the end of the method), and so forth. The exact checks performed during verification are dependent on the implementation of the virtual machine 104. In some cases, verification may cause additional classes to be loaded, but does not necessarily require those classes to also be linked before proceeding. For example, assume Class A contains a reference to a static field of Class B. During verification, the virtual machine 104 may check Class B to ensure that the referenced static field actually exists, which might cause loading of Class B, but not necessarily the linking or initializing of Class B. However, in some embodiments, certain verification checks can be delayed until a later phase, such as being checked during resolution of the symbolic references. For example, some embodiments may delay checking the access permissions for symbolic references until those references are being resolved.

To prepare a class, the virtual machine 104 initializes static fields located within the field and method data 306 for the class to default values. In some cases, setting the static fields to default values may not be the same as running a constructor for the class. For example, the verification process may zero out or set the static fields to values that the constructor would expect those fields to have during initialization.

During resolution, the virtual machine 104 dynamically determines concrete memory address from the symbolic references included in the run-time constant pool 304 of the class. To resolve the symbolic references, the virtual machine 104 utilizes the class loader 107 to load the class identified in the symbolic reference (if not already loaded). Once loaded, the virtual machine 104 has knowledge of the memory location within the per-class area 303 of the referenced class and its fields/methods. The virtual machine 104 then replaces the symbolic references with a reference to the concrete memory location of the referenced class, field, or method. In an embodiment, the virtual machine 104 caches resolutions to be reused in case the same class/name/descriptor is encountered when the virtual machine 104 processes another class. For example, in some cases, class A and class B may invoke the same method of class C. Thus, when resolution is performed for class A, that result can be cached and reused during resolution of the same symbolic reference in class B to reduce overhead.

In some embodiments, the step of resolving the symbolic references during linking is optional. For example, an embodiment may perform the symbolic resolution in a “lazy” fashion, delaying the step of resolution until a virtual machine instruction that requires the referenced class/method/field is executed.

During initialization, the virtual machine 104 executes the constructor of the class to set the starting state of that class. For example, initialization may initialize the field and method data 306 for the class and generate/initialize any class instances on the heap 302 created by the constructor. For example, the class file 200 for a class may specify that a particular method is a constructor that is used for setting up the starting state. Thus, during initialization, the virtual machine 104 executes the instructions of that constructor.

In some embodiments, the virtual machine 104 performs resolution on field and method references by initially checking whether the field/method is defined in the referenced class. Otherwise, the virtual machine 104 recursively searches through the super-classes of the referenced class for the referenced field/method until the field/method is located, or the top-level superclass is reached, in which case an error is generated.

3. Module Elements of a Module in a Module System

One or more embodiments are applicable to a module system. Each module within a module system corresponds to a respective set of code (referred to as “module code”). Each module is associated with one or more module elements. A module element, as referred to herein, corresponds to a portion of the module code. A module element (portion of module code) may itself include additional module elements (sub-portions of module code).

Module systems implemented in different programming languages may be defined with different types of module elements. Some examples, described herein, refer to the specific module elements of a module in a Java Module System for purposes of explanation. However, embodiments are equally applicable to module elements of different types in module systems implemented in other programming languages.

In the Java Module System, each module includes one or more packages. Each package includes one or more classes. Each class includes one or more class members such as fields and methods. Methods, as referred to herein, include constructors which may be invoked for the creation of an object by instantiating classes. A module element, as referred to herein with respect to the Java Module System, may include a package, a class, or a class member.

Exposing Module Elements

In an embodiment, a module element of a module may or may not be exposed to another module. In the Java Module System, a package may be exposed by a module when a module descriptor, corresponding to the module, includes an “exports” expression with the package identified as a parameter. The package may be exported to a set of specified modules (referred to as “qualified export”) or to all other modules in the module system (referred to as “unqualified export”).

The module element, of a provider module, may be exposed to a consumer module by the provider module if any of a set of conditions are met. The set of conditions may include, but are not limited to (a) a declaration within the descriptor of the provider module that exposes the module element to the consumer module via a qualified or unqualified export, (b) a user instruction received via an interface (e.g., a command line interface), (c) a determination by the run-time environment based on detection of a triggering event associated with permissions for exposing the module element, or (d) any other instruction that instructs a module system to expose the module element.

A particular module element may be exposed by exposing of the particular module element itself or by exposing another module element which includes the particular module element. In one example, a class may be exposed by exposing a package which includes the class. Class members of the class are also exposed by exposing of the package which includes the class.

One or more embodiments relate to accessing module elements of a module in a module system. The module attempting the access is referred to herein as a consumer module and the module being accessed is referred to herein as a provider module. A module may function as either a consumer module or provider module for different access operations.

In an embodiment, determining whether a module element of a provider module may be accessed by a consumer module is based, at least in part, on whether the module element in the provider module as been exposed to the consumer module. Access controls which determine whether a module element of a provider module can be accessed by a consumer module are further described in Section 5. “Controlling Access to Module Elements.”

Access Modifiers for Module Elements

In an embodiment, a module element is declared with an access modifier. The access modifier identifies an accessibility configuration of the module element. The accessibility configuration declares that the module element is (a) publicly accessible or (b) not publicly accessible. In one example, the modifier “public” indicates that a module element is publicly accessible and the modifier “private” indicates that the module element is not publicly accessible. However, the declared access modifier does not by itself control whether the module element is accessible or inaccessible from outside of the module. Access controls which determine whether a module element of a provider module can be accessed by a consumer module are further described in Section 5. “Controlling Access to Module Elements.”

4. Operations which May Require Accessing a Module Element of a Provider Module by a Consumer Module

In an embodiment, different kinds of operations require access to a module element of a provider module by a consumer module.

Operations may be performed on byte code to enumerate, analyze, and/or categorize sections of the byte code. Some examples of operations for accessing module elements include reflection operations identified in the Java reflection API.

In an embodiment, an operation includes getting or setting a value of a module element where (a) the module element represents a field, (b) the getting or setting is performed with respect to an object, and (c) the object is an instance of another module element (e.g., a class which includes the field). An example set of operations include, but are not limited to:

-   -   (a) getField(String name): Returns a Field object that reflects         the specified field of the class or interface represented by the         Class object upon which the command is executed.     -   (b) getFields( ): Returns an array containing Field objects         reflecting all the fields of the class or interface represented         by the Class object upon which the command is executed.     -   (c) getDeclaredFields( ): Returns an array of Field objects         reflecting all the fields declared by the class or interface         represented by the Class object upon which the command is         executed.     -   (d) getDeclaredMethods( ): Returns an array of Method objects         reflecting all the methods declared by the class or interface         represented by the Class object upon which the command is         executed.     -   (e) getSuperclass( ): Returns the Class representing the         superclass of the entity (class, interface, primitive type or         void) represented by the Class upon which the command is         executed.     -   (f) set(Object obj, Object value): Sets the value of the field         represented by the Field object upon which the command is         executed, on the specified object argument to the specified new         value.     -   (g) get(Object obj): Returns the value of the field represented         by the Field upon which the command is executed, on the         specified object.

In an embodiment, an operation includes a consumer module invoking the module element of a provider module. Module elements which are methods may be invoked with or without reflection techniques. One example command for invoking a method using reflection includes java.lang.reflect.Method.invoke( ). The first argument is the object instance on which a particular method is to be invoked. If the method is static, the first argument may be null. Subsequent arguments are the method's parameters.

In an embodiment, an operation includes a consumer module instantiating the module element of a provider module. A class (first module element of provider module) may be instantiated by a consumer module by invoking a constructor (second module element of provider module) of the class.

In an example, a class Spaceship is a first module element in a provider module. The class Spaceship includes a second module element which is a method declaration fireMissile( ). A separate class CommandCenter is a module element in a consumer module. The class CommandCenter (module element of consumer module) may include operations to (a) instantiate an object of type Spaceship (module element of provider module) and (b) invoke the method fireMissile( ) (module element of provider module) on the instance of SpaceShip from (a).

5. Controlling Access to Module Elements

As noted above, one or more operations require access to a module element of a provider module by a consumer module. One or more embodiments include controlling access to the module element of the provider module by the consumer module. Controlling access includes allowing access or prohibiting access. If access to the module element of the provider module by the consumer module is allowed, then the operation is successfully compiled or executed. If the access to the module element of the provider module by the consumer module is prohibited, then the operation may not successfully compile and/or may not successfully execute. Factors, as described herein, for controlling access to a particular type of module element may be applicable for controlling access to another type of module element.

FIG. 4 illustrates an example of a module in the Java Module System in accordance with one or more embodiments. Other modules (defined using the Java Module System or other module systems) may include more, less, and/or different module elements than illustrated in FIG. 4. A module (e.g., module 402) may include any number of packages. A package (e.g., package 404) may include any number of classes. A class (e.g., class 406) may include any number of class members (e.g., class member 408).

One or more embodiments include controlling access to module elements (i.e., package 404, class 406, or class member 408) of a provider module (e.g., module 402) by a consumer module (e.g., module 430). In order for module 430 to access class member 408 of module 402, module 430 may need access permissions to access (a) class member 408 itself, (b) class 406 which includes class member 408, and (c) package 404 which includes class 406. Furthermore, access controls applicable to a module element (e.g., class 406) may determine whether an operation that accesses an object, created by instantiating the module element, is allowed or prohibited. In an example, access to obtain or modify a value of field of an object is allowed or prohibited based on access controls for the particular class which is instantiated to create the object.

FIG. 5 illustrates an example set of steps for allowing or prohibiting access to a module element of a provider module by a consumer module. Steps described below with reference to FIG. 5 may be performed prior to and/or during runtime. A compiler, interpreter, and/or runtime environment may perform one or more of the steps described below.

Initially, an operation by a consumer module that attempts to access a module element of a provider module is identified (Step 502). The operation may be identified by a compiler during a compilation process. The operation may be identified by the runtime environment when execution of the operation is requested. Some examples of kinds of operations which require access to a module element are indicated above in Section 4, titled “Operations which may require accessing a module element of a provider module by a consumer module.”

Responsive to identifying an operation by a consumer module that attempts to access a module element of a provider module, a check is necessary to determine if the consumer module has the necessary permissions to access the module element of the provider module. The check is a multi-step process as described below.

In an embodiment, a determination is made whether the module element of the provider module has been exposed to the consumer module (Step 504). As noted above, a particular module element of a provider module may be exposed to the consumer module if either (a) the particular module element has itself been exposed to the consumer module or (b) if a second module element which includes the particular module element has been exposed to the consumer module. In the Java module system, if a package in a provider module has been exposed to a consumer module, then all of the classes within the package and the class members within the classes have been exposed to the consumer module. In the example illustrated in FIG. 4, exposing package 404 of module 402 to module 430 includes exposing class 406 and class 408 to module 430. Package 404 of module 402 may be exposed to module 430 with a qualified export which specifically identifies module 430. Package 404 of module 402 may be exposed to module 430 with an unqualified export to all modules in the module system (without specifically identifying module 430).

If the module element of the provider module has not been exposed to the consumer module, then the consumer module is strictly prohibited from accessing the module element of the provider module (Step 506). Access to the module element of the provider module by the consumer module is strictly prohibited regardless of (a) an access modifier in the module element declaration, (b) an accessibility override configuration expressed for the module element (described below), or (c) a level of access associated with the operation that attempts to access the module element (described below). Strictly prohibiting access may include generating a compile time error and/or runtime error (e.g., throwing an exception) which prevents execution of an operation that attempts to access the module element.

In the example illustrated in FIG. 4, if class member 408 has not been exposed to module 430, then access to class member 408 by module 430 is strictly prohibited. The strict prohibition to non-exposed class member 408 is applicable even if (a) class member 408 and class 406 are declared with public access modifiers (b) an accessibility override configuration is set to override any non-public access modifiers, and (c) the attempt to access class member 408 relies upon an operation with a highest possible level of access. Similarly, if class 406 has not been exposed to module 430, then access to class 406 by module 430 is strictly prohibited.

If a determination is made in Operation 504 that the module element of the provider module has been exposed to the consumer module, then access may or may not be allowed. In other words, exposing of the module element of the provider module to the consumer module does not guarantee that the consumer module is allowed to access the module element. Allowing or prohibiting access to the exposed module element of the provider module by the consumer module depends on a set of factors as described below.

In an embodiment, a determination is made whether the exposed module element is declared with a public access modifier (Step 508). The module element declaration may be examined to determine if a public access modifier or a non-public access modifier is configured for the exposed module element. Furthermore, if the exposed module element is included within another parent module element with an access modifier, then a check is performed to determine if the declaration of the parent module element includes a public access modifier or a non-public access modifier. For example, if the exposed module element is a class member of particular class, then the access modifier of each of the class member declaration and the class declaration are examined to determine if both include public access modifiers.

If the module element (and any parent module element with an access modifier) is (are) declared with a public access modifier, then access to the module element of the provider module by the consumer module is allowed (Step 514). Allowing access to the module element of the provider module by the consumer module allows for successful compilation and/or execution of the operation, which attempts to access the module element.

If the exposed module element (or if any parent module element of the module element) are declared with a non-public access modifier, then additional analysis is needed to determine if access to the exposed module element is to be allowed or prohibited. Access to the exposed module element with a non-public access modifier may depend on a level of access associated with the operation attempting access. FIG. 5 defines an operation, with a minimum level of access required to access an exposed module element with a non-public modifier, as a reflective operation with an accessibility override configuration set for the exposed module element (detailed below). However, other embodiments are equally applicable to any system in which different operations are associated with different levels of access. For example, a first operation (in a consumer module) with a first level of access is allowed to access a non-public class member of a public class in an exposed package of a provider module. However, the first operation with the first level of access is prohibited from accessing a non-public class member of a non-public class in the exposed package of the provider module. A second operation (in the same consumer module) with a second level of access (higher than the first level of access) is allowed to access the non-public class member of the non-public class in the exposed package of the provider module. Accordingly, the specific operations 510 and 512 of FIG. 5 described below should be understood as an example set of rules for determining access to an exposed module element with a non-public modifier. The specific operations 510 and 512 should not be construed as limiting the scope of other embodiments in which operations are defined with a different set of access levels.

Continuing with FIG. 5, in an embodiment, an exposed module element with a non-public access modifier may be accessible if (a) the operation is a reflective operation (Step 510) and (b) an accessibility override configuration is set for the exposed module element being accessed (Step 512). Accordingly, if the operation is a reflective operation with an accessibility override configuration set for the module element being accessed, then access to the module element is allowed (Step 514). In an embodiment, an accessibility override configuration is available to a consumer module for accessing a module element of a provider module. The accessibility override configuration may be available to the consumer module independent of any configuration for the provider module even though the accessibility override configuration is being set to access the module element of the provider module.

In an example, a reflective operation (from the Java reflection API) includes get(Object obj) which returns the value of the field represented by the Field (on which the command is executed), on the specified object. The reflective operation further includes setAccessible( ) which sets the accessibility override configuration for the exposed module element with a non-public modifier. The reflective operation with the accessibility override configuration is allowed to access the exposed module element with a non-public modifier. The exposed module element being an element of a provider module which is being accessed by a consumer module.

6. Miscellaneous Extensions

Embodiments are directed to a system with one or more devices that include a hardware processor and that are configured to perform any of the operations described herein and/or recited in any of the claims below.

In an embodiment, a non-transitory computer readable storage medium comprises instructions which, when executed by one or more hardware processors, causes performance of any of the operations described herein and/or recited in any of the claims.

Any combination of the features and functionalities described herein may be used in accordance with one or more embodiments. In the foregoing specification, embodiments have been described with reference to numerous specific details that may vary from implementation to implementation. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The sole and exclusive indicator of the scope of the invention, and what is intended by the applicants to be the scope of the invention, is the literal and equivalent scope of the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction.

7. Hardware Overview

According to one embodiment, the techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, portable computer systems, handheld devices, networking devices or any other device that incorporates hard-wired and/or program logic to implement the techniques.

For example, FIG. 6 is a block diagram that illustrates a computer system 600 upon which an embodiment of the invention may be implemented. Computer system 600 includes a bus 602 or other communication mechanism for communicating information, and a hardware processor 604 coupled with bus 602 for processing information. Hardware processor 604 may be, for example, a general purpose microprocessor.

Computer system 600 also includes a main memory 606, such as a random access memory (RAM) or other dynamic storage device, coupled to bus 602 for storing information and instructions to be executed by processor 604. Main memory 606 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 604. Such instructions, when stored in non-transitory storage media accessible to processor 604, render computer system 600 into a special-purpose machine that is customized to perform the operations specified in the instructions.

Computer system 600 further includes a read only memory (ROM) 608 or other static storage device coupled to bus 602 for storing static information and instructions for processor 604. A storage device 610, such as a magnetic disk or optical disk, is provided and coupled to bus 602 for storing information and instructions.

Computer system 600 may be coupled via bus 602 to a display 612, such as a cathode ray tube (CRT), for displaying information to a computer user. An input device 614, including alphanumeric and other keys, is coupled to bus 602 for communicating information and command selections to processor 604. Another kind of user input device is cursor control 616, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 604 and for controlling cursor movement on display 612. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.

Computer system 600 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 600 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 600 in response to processor 604 executing one or more sequences of one or more instructions contained in main memory 606. Such instructions may be read into main memory 606 from another storage medium, such as storage device 610. Execution of the sequences of instructions contained in main memory 606 causes processor 604 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.

The term “storage media” as used herein refers to any non-transitory media that store data and/or instructions that cause a machine to operation in a specific fashion. Such storage media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 610. Volatile media includes dynamic memory, such as main memory 606. Common forms of storage media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge.

Storage media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between storage media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 602. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.

Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 604 for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 600 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 602. Bus 602 carries the data to main memory 606, from which processor 604 retrieves and executes the instructions. The instructions received by main memory 606 may optionally be stored on storage device 610 either before or after execution by processor 604.

Computer system 600 also includes a communication interface 618 coupled to bus 602. Communication interface 618 provides a two-way data communication coupling to a network link 620 that is connected to a local network 622. For example, communication interface 618 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding kind of telephone line. As another example, communication interface 618 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 618 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link 620 typically provides data communication through one or more networks to other data devices. For example, network link 620 may provide a connection through local network 622 to a host computer 624 or to data equipment operated by an Internet Service Provider (ISP) 626. ISP 626 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 628. Local network 622 and Internet 628 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 620 and through communication interface 618, which carry the digital data to and from computer system 600, are example forms of transmission media.

Computer system 600 can send messages and receive data, including program code, through the network(s), network link 620 and communication interface 618. In the Internet example, a server 630 might transmit a requested code for an application program through Internet 628, ISP 626, local network 622 and communication interface 618.

The received code may be executed by processor 604 as it is received, and/or stored in storage device 610, or other non-volatile storage for later execution.

In the foregoing specification, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The sole and exclusive indicator of the scope of the invention, and what is intended by the applicants to be the scope of the invention, is the literal and equivalent scope of the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. 

What is claimed is:
 1. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, cause performance of steps comprising: identifying an operation, expressed in a first set of module code, that attempts to access a module element of a second set of module code; wherein the module element is declared with a non-public modifier; determining whether the module element has been exposed to the first set of module code by the second set of module code; determining whether the operation attempts to access the module element using an accessibility override configuration available to the first set of module code; responsive to determining that (a) the module element has been exposed to the first set of module code by the second set of module code and (b) the operation attempts to access the module element using an accessibility override configuration available to the first set of module code, and only when the module element has been exposed to the first set of module code by the second set of module code: allowing the operation to access the module element using the accessibility override configuration available to the first set of module code.
 2. The medium of claim 1, wherein determining whether the operation attempts to access the module element using an accessibility override configuration available to the first set of module code is performed in response to determining that the module element has been exposed to the first set of module code by the second set of module code.
 3. The medium of claim 1, wherein the operation comprises a reflective operation.
 4. The medium of claim 1, wherein the operation comprises invoking the module element.
 5. The medium of claim 1, wherein the operation comprises modifying a value of an object created by instantiating the module element.
 6. The medium of claim 1, wherein the operation comprises obtaining a value of an object created by instantiating the module element.
 7. The medium of claim 1, wherein the operation comprises instantiating the module element.
 8. A method comprising: identifying an operation, expressed in a first set of module code, that attempts to access a module element of a second set of module code; wherein the module element is declared with a non-public modifier; determining whether the module element has been exposed to the first set of module code by the second set of module code; determining whether the operation attempts to access the module element using an accessibility override configuration available to the first set of module code; responsive to determining that (a) the module element has been exposed to the first set of module code by the second set of module code and (b) the operation attempts to access the module element using an accessibility override configuration available to the first set of module code, and only when the module element has been exposed to the first set of module code by the second set of module code: allowing the operation to access the module element using the accessibility override configuration available to the first set of module code.
 9. The method of claim 8, wherein determining whether the operation attempts to access the module element using an accessibility override configuration available to the first set of module code is performed in response to determining that the module element has been exposed to the first set of module code by the second set of module code.
 10. The method of claim 8, wherein the operation comprises a reflective operation.
 11. The method of claim 8, wherein the operation comprises invoking the module element.
 12. The method of claim 8, wherein the operation comprises modifying a value of an object created by instantiating the module element.
 13. The method of claim 8, wherein the operation comprises obtaining a value of an object created by instantiating the module element.
 14. The method of claim 8, wherein the operation comprises instantiating the module element.
 15. A system comprising: at least one device including a hardware processor; the system being configured to perform steps comprising: identifying an operation, expressed in a first set of module code, that attempts to access a module element of a second set of module code; wherein the module element is declared with a non-public modifier; determining whether the module element has been exposed to the first set of module code by the second set of module code; determining whether the operation attempts to access the module element using an accessibility override configuration available to the first set of module code; responsive to determining that (a) the module element has been exposed to the first set of module code by the second set of module code and (b) the operation attempts to access the module element using an accessibility override configuration available to the first set of module code, and only when the module element has been exposed to the first set of module code by the second set of module code: allowing the operation to access the module element using the accessibility override configuration available to the first set of module code.
 16. The system of claim 15, wherein determining whether the operation attempts to access the module element using an accessibility override configuration available to the first set of module code is performed in response to determining that the module element has been exposed to the first set of module code by the second set of module code.
 17. The system of claim 15, wherein the operation comprises a reflective operation.
 18. The system of claim 15, wherein the operation comprises invoking the module element.
 19. The system of claim 15, wherein the operation comprises modifying a value of an object created by instantiating the module element.
 20. The system of claim 15, wherein the operation comprises obtaining a value of an object created by instantiating the module element.
 21. The system of claim 15, wherein the operation comprises instantiating the module element. 